home *** CD-ROM | disk | FTP | other *** search
- From: khollis@bitsink.gbdata.com (K. Hollis)
- Subject: Dialog Box Proposal Part 1
- Date: Sat, 25 Jun 1994 15:31:24 +0000 (GMT)
- Mime-Version: 1.0
- Precedence: bulk
-
- --- Forgive me... This was edited on an Atari ST, and I have newlines... ---
- --- Vote on these, or make changes as you wish. Remember, LTMF-2 will have --
- --- all proposals herein. ---
- ::: Ken Hollis / Bitgate Software / Developer of Let 'em Fly Revision II :::
-
-
- ** Dialog box look and feel proposal **
- ** Proposal by Ken Hollis of Bitgate Software **
-
- >>> PART 1 <<<
-
- (Some of these proposals for the look-and-feel may be a practical idea,
- some may not. Please, feel free to vote on any of these, or BASH any
- ideas that you do not agree with. I will eventually compile all of the
- ideas and combine them in Let 'em Fly II.)
-
- Just for the record, LTMF-2 will be GEM List Level #1 Compliant.
-
- -------------------------------------------------------------------------
-
- Handling sliders:
- """""""""""""""""
- Sliders MUST be handled in a redraw-as-you-drag (or active-drawing)
- method in order to provide full functionality. Any sliders that are
- designed to display information (such as scaling percentages, etc) should
- be displayed either within the slider bar, or to the direct right or
- left of the slider track. Sliders that take time to draw information
- based on their position must be ghost-drag type.
-
- -------------------------------------------------------------------------
-
- Handling buttons:
- """""""""""""""""
- Hotkeys must be identified by either an underline, an inverted character,
- or as a reddened (or otherwise) character. The hotkey button must be
- selectable by keyboard with the ALT- key, and MUST be an alphanumeric
- character (ie. 0-9, A-Z). The activation characters MUST be in uppercase
- to avoid confusion. Any characters that are typed with the ALT-key
- combination (unless in an editable field) are automatically converted to
- uppercase, and checked for the hotkey.
-
- If an editable text field is in the dialog box, the only way the hotkey
- can be accessed is by pressing ALT- and the key. If no editable fields
- are in the dialog box, simply have button activation by pressing the
- activation character; DO NOT require an ALT- key combination.
-
- -------------------------------------------------------------------------
-
- Editable objects:
- """""""""""""""""
- If the mouse is placed over an editable text field, the mouse MUST change
- to a TEXT CURSOR while the mouse is over it. It must be changed back to
- its original form when moved away.
-
- The text cursor must be manipulated in the following way:
-
- - Arrow-UP : Moves the text cursor to the previous field. If
- it is at the first editable field, wrap around to
- the last editable field.
- + SHIFT : Move to the first editable field. If already at
- the first editable field, move the text cursor to
- the start of the editable field, regardless of any
- text already in the field.
- + SHIFT-CTRL : Insert text from clipboard at its current
- position, then move the counter up one. Press
- again to get the next previously entered string.
- - Arrow-DOWN : Moves the text cursor to the next field. If it is
- at the last editable field, wrap around to the
- first editable field.
- + SHIFT : Same as up but to the last field.
- + SHIFT-CTRL : Same as SHIFT-CTRL-ARROW-UP, but in the opposite
- direction, respectively.
- - Arrow-LEFT : Move the text cursor one to the left, or scroll
- extended length of text to the left.
- + SHIFT : Move text cursor to the beginning of the text in
- an editable field.
- + CONTROL : Move text cursor to the beginning of a word before
- its immediate position.
- - Arrow-RIGHT : Same as left, but move right respectively.
- - Insert : Toggle insert/overwrite mode (change cursor too.)
- + SHIFT : Bring up a character table to select characters to
- input into the editable field.
- - ClrHome : Acts exactly the same as SHIFT-ARROW-UP.
- + SHIFT : Acts exactly the same as SHIFT-ARROW-DOWN.
- + CONTROL : Clears out all editable text fields.
- - Delete : Delete character in front of cursor.
- + LSHIFT : Delete all text to left of cursor.
- + RSHIFT : Delete all text to right of cursor.
- + L&RSHIFT : Delete entire editable field. (Same as [ESC])
-
- -- Level 1 Compliant listing (with modifications where needed) --
-
- < Clipboard functions >
- - CTRL-C : Copy text to clipboard, don't clear out field.
- - CTRL-V : Paste last copied or cut item back.
- - CTRL-X : Cut text to clipboard, and clear out the field.
- - CTRL-UNDO : Clear/empty out clipboard information.
-
- < Extended editing >
- - CTRL-BS : Delete word to the left of cursor.
- - CTRL-DELETE : Delete word to the right of cursor.
- - CTRL-Y : Delete/Clear out editable field.
- - ESC : Same as CTRL-Y.
- - SHIFT-CTRL-Z : Same as SHIFT-INSERT.
-
- -------------------------------------------------------------------------
-
- Identifying clipboard location:
- """""""""""""""""""""""""""""""
- Instead of having the clipboard at a set place (like U:\CLIP or whatever)
- why not have it set in an environmental variable? I propose that the
- following four environmental variables be reserved for clipboard
- directory locations:
-
- CLIPBRD, SCRAPDIR -- These are standards to GEM
- TMP, TEMP -- These are standards to Unix/Linux
-
- -------------------------------------------------------------------------
-
- Extended Object Types:
- """"""""""""""""""""""
- Atari Corp. has announced in the MultiTOS documentation that it fully
- supports and authorizes all usage of InterFace Extended Object Types.
- With that in mind, why not use their indices? The following is a list
- of their indices, and some extras that I have used in my library called
- "WinLIB PRO". The list is as follows (with specifications on how the
- objects should be setup):
-
- FLYING (17) - This lets you move the dialog box anywhere on the
- screen. Objects should be TOUCHEXIT.
- CUSTOM (18) - This specifies objects that have "X" when selected, or
- a filled circle for radio buttons. "X" objects should
- be SELECTABLE (can be any type), and CIRCLE buttons
- must be RADIO BUTTON type.
- UNDERLINE (19) - This specifies an underlined object. Double underline
- should be specified with OBFLAGS15. Objects can be
- any type except SELECTABLE or TOUCHEXIT.
- SCALE (20) - This scales an icon or image to correct height based on
- screen resolution. Object type must be ICON or IMAGE,
- and can have any flags.
- BOXFRAME (21) - This specifies a box with a boxframe in the upper left,
- center, or right of the top of a box with a header. It
- can be boxed by setting OBFLAGS14. Must be BUTTON or
- BOXTEXT, with no set flags.
- ENHANCED (23) - An object that has a hotkey. Can be any type.
-
- -------------------------------------------------------------------------
-
- New Level Compliant Proposal:
- """""""""""""""""""""""""""""
- Hey, when you design compliants, you're always gonna have someone who
- disagrees with some part of it.
-
- Why not, instead of having "G1" or "G2" proposals for document editing
- programs, which is EXACTLY what that they were designed for, why not
- have this:
-
- <For document viewers and editors>
- DG1 - GEM List Level 1 Compliant : Follows keyboard shortcut guide
- DG2 - GEM List Level 2 Compliant : As above, supporting conf file as well
-
- <For GEM libraries and GEM dialog replacement programs>
- GG1 - GEM List Level 3 Compliant : Follows editing guide and clipbd. above
- GG2 - GEM List Level 4 Compliant : As above, with EObTs and sliders
-
- -------------------------------------------------------------------------
-
- More in the second list. Any objections to these so far?
-
- -- Ken (Bitgate Software)
-